Re: what are realistic threats?

• To: hallam@dxal18.cern.ch
• Subject: Re: what are realistic threats?
• From: Karl Auerbach <karl@cavebear.com>
• Date: Sun, 2 Oct 94 12:32:38 PDT
• Cc: tmplee@mr.net, www-security@ns1.rutgers.edu, hallam@dxal18.cern.ch
• In-Reply-To: hallam@dxal18.cern.ch's message of Thu, 29 Sep 94 11:07:46 +0100 <9409291007.AA26803@dxal18.cern.ch>
• Originating-Client: pax
• Reply-To: Karl Auerbach <karl@cavebear.com>
• Repository: cavebear

 >This is why I think we need a standalone certificate scheme. The program may
 >reside on any server but has a certificate signed by the producer. Although
 >single rooted authentication hierarchies have problems most people would trust
 >the signature if signed by USGovt, MIT, W3O, AMEX and Peter Wright.

Different people have different definitions of "security" and you
might not be happy with the author's definition as embedded in his/her
program/script even if you can prove you have an authentic copy.

		--karl--

• Re: what are realistic threats?
• From: szabo@netcom.com (Nick Szabo)
• Re: what are realistic threats?
• From: hallam@dxal18.cern.ch

• Re: what are realistic threats?
• From: hallam@dxal18.cern.ch

• Previous: Re: Source-routed URLs
• Next: Re: what are realistic threats?
• Index(es):
  • Index
  • Thread